<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
 <head>
  <meta content="Copyright &copy; 2023 Thales. All Rights Reserved." name="copyright"/>
  <meta content="text/html;charset=utf-8" http-equiv="content-type"/>
  <meta content="text/css" http-equiv="Content-Style-Type"/>
  <title>
   Arcadia Reference - From Definition &amp; Design to Validation
  </title>
  <link href="../../scripts/jquery-treeview/jquery.treeview.css" rel="stylesheet"/>
  <script src="../../scripts/jquery-treeview/lib/jquery-1.11.1.js" type="text/javascript">
  </script>
  <script src="../../scripts/jquery-treeview/jquery.treeview.js" type="text/javascript">
  </script>
  <link href="../../css/simpletree.css" rel="stylesheet" type="text/css"/>
  <link href="../../css/content.css" media="screen, projection" rel="stylesheet" title="default" type="text/css"/>
  <style>
   body {}
			.treeview {
				background-color: white ;
			}
	
			.treeview ul{ /*CSS for Simple Tree Menu*/
				background-color: white;
				font-size: 12px;
			}
	
			.treeview li{ /*Style for LI elements in general (excludes an LI that contains sub lists)*/
				background-color: white;
			}
  </style>
 </head>
 <body>
  <img src="../icon/logo_arcadia_small.png" style="float:left;width:50px;height:50px;"/>
  <nav>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#">
    ARCADIA
   </a>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#landscape">
    Engineering Landscape
   </a>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#userGuide">
    User Guide
   </a>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#reference">
    Reference Manual
   </a>
  </nav>
  <p>
   <br/>
  </p>
  <div id="content">
   <img alt="FunctionalChain" src="../icon/FunctionalChain.png" style="float:left; margin-right:10px"/>
   <h1>
    <a href="../ARCADIA/c2f4728fdb244205bf04129d1a76ec1b.html">
     From Definition &amp; Design to Validation
    </a>
   </h1>
   <p style="margin-top:3px; margin-bottom:3px">
    <span class="elementMetaClass">
     Engineering Process
    </span>
    <p>
    </p>
   </p>
   <em class="elementPath">
    <a href="../ARCADIA/ad8c8a109fa64f039584c15108639254.html">
     Engineering Capabilities
    </a>
    &gt;
    <a href="../ARCADIA/4e8472cf52d44160a41ed722c73b1861.html">
     Support  Collaboration in Engineering
    </a>
    &gt;
    <a href="../ARCADIA/c2f4728fdb244205bf04129d1a76ec1b.html">
     From Definition &amp; Design to Validation
    </a>
   </em>
   <p>
    <p>
     <strong>
      Challenge: How to verify adequacy of Solution to Need, based on former engineering activities and assets
     </strong>
     .
    </p>
    <ul>
     <li>
      Build the IVV strategy based on operational and system need analysis and customer value analysis to deliver appropriate capabilities to customer.
     </li>
     <li>
      Define test campaigns and test cases according to these capabilities, based on functional chains and scenarios describing these capabilities.
     </li>
     <li>
      Use links between need and solution descriptions to justify the strategy, and compliance with user requirements.
     </li>
    </ul>
   </p>
   <h2>
    Related Diagrams
   </h2>
   <div>
    <p class="diagram-name" id="_lOeNIJQyEeqxb5_tqwKmHg">
     4  From Definition  Design to Validation
    </p>
    <p class="diagram">
     <img alt="4  From Definition  Design to Validation" src="c2f4728fdb244205bf04129d1a76ec1b/_lOeNIJQyEeqxb5_tqwKmHg.jpg" usemap="#4  From Definition  Design to Validation__lOeNIJQyEeqxb5_tqwKmHg_PositionMap"/>
     <br/>
     <br/>
     <map name="4  From Definition  Design to Validation__lOeNIJQyEeqxb5_tqwKmHg_PositionMap">
      <area alt="8801691110aa4b1581f8c2bfff97d5f0" coords="780,122,880,172" group="8801691110aa4b1581f8c2bfff97d5f0" href="../ARCADIA/8801691110aa4b1581f8c2bfff97d5f0.html#id88016911-10aa-4b15-81f8-c2bfff97d5f0" shape="rect"/>
      <area alt="65458973c7084233b791dc81b9246191" coords="850,206,950,256" group="65458973c7084233b791dc81b9246191" href="../ARCADIA/65458973c7084233b791dc81b9246191.html#id65458973-c708-4233-b791-dc81b9246191" shape="rect"/>
      <area alt="ad6b0fea2dfc4181b89d719acdf340c4" coords="730,32,830,82" group="ad6b0fea2dfc4181b89d719acdf340c4" href="../ARCADIA/ad6b0fea2dfc4181b89d719acdf340c4.html#idad6b0fea-2dfc-4181-b89d-719acdf340c4" shape="rect"/>
      <area alt="b273e2e253ef42f0a6d1c63f53b8a3a5" coords="10,11,140,66" group="b273e2e253ef42f0a6d1c63f53b8a3a5" href="../ARCADIA/b273e2e253ef42f0a6d1c63f53b8a3a5.html#idb273e2e2-53ef-42f0-a6d1-c63f53b8a3a5" shape="rect"/>
      <area alt="c354668558fc433fa1124e7b02e6bc7f" coords="10,81,140,136" group="c354668558fc433fa1124e7b02e6bc7f" href="../ARCADIA/c354668558fc433fa1124e7b02e6bc7f.html#idc3546685-58fc-433f-a112-4e7b02e6bc7f" shape="rect"/>
      <area alt="21963be2f5f544798045079ed00879fa" coords="10,295,140,350" group="21963be2f5f544798045079ed00879fa" href="../ARCADIA/21963be2f5f544798045079ed00879fa.html#id21963be2-f5f5-4479-8045-079ed00879fa" shape="rect"/>
      <area alt="dd460dc8ee0b4ceba0c0135c7c103ba9" coords="10,150,140,205" group="dd460dc8ee0b4ceba0c0135c7c103ba9" href="../ARCADIA/dd460dc8ee0b4ceba0c0135c7c103ba9.html#iddd460dc8-ee0b-4ceb-a0c0-135c7c103ba9" shape="rect"/>
      <area alt="38c7424f5c11476490db367b0b43bc42" coords="10,225,140,280" group="38c7424f5c11476490db367b0b43bc42" href="../ARCADIA/38c7424f5c11476490db367b0b43bc42.html#id38c7424f-5c11-4764-90db-367b0b43bc42" shape="rect"/>
      <area alt="d260034d335e47c98fbec6f97f023fa3" coords="350,11,461,61" group="d260034d335e47c98fbec6f97f023fa3" href="../ARCADIA/d260034d335e47c98fbec6f97f023fa3.html#idd260034d-335e-47c9-8fbe-c6f97f023fa3" shape="rect"/>
      <area alt="9795c75eab3749b6ba4faf74866fbe90" coords="350,298,461,348" group="9795c75eab3749b6ba4faf74866fbe90" href="../ARCADIA/9795c75eab3749b6ba4faf74866fbe90.html#id9795c75e-ab37-49b6-ba4f-af74866fbe90" shape="rect"/>
      <area alt="fb4a1233e07c4fdfa6a376293041489c" coords="350,150,461,200" group="fb4a1233e07c4fdfa6a376293041489c" href="../ARCADIA/fb4a1233e07c4fdfa6a376293041489c.html#idfb4a1233-e07c-4fdf-a6a3-76293041489c" shape="rect"/>
     </map>
    </p>
    <p class="diagram-description">
     <p>
      This figure describes
     </p>
     <p>
      <strong>
       How to verify adequacy of Solution to Need, based on former engineering activities and assets
      </strong>
      .
     </p>
     <ul>
      <li>
       Build the IVV strategy based on operational and system need analysis and customer value analysis to deliver appropriate capabilities to customer.
      </li>
      <li>
       Define test campaigns and test cases according to these capabilities, based on functional chains and scenarios describing these capabilities.
      </li>
      <li>
       Use links between need and solution descriptions to justify the strategy, and compliance with user requirements.
      </li>
     </ul>
     <p>
      For each step of this process, involving an engineering task or activity, the description gives some hints and methological recommendations. These recommendations are complementary with the description of the involved activity per se, in the context of the engineering concern and the process.
     </p>
    </p>
   </div>
   <h2>
    Contribution of each engineering activity to this process
   </h2>
   <table>
    <tr>
     <th>
      Engineering activity
     </th>
     <th>
      Specifics of activity for this process
     </th>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/b273e2e253ef42f0a6d1c63f53b8a3a5.html">
       Perform CUSTOMER OPERATIONAL NEED ANALYSIS
      </a>
     </td>
     <td>
      <p>
       The IVV strategy will order deliveries according to the customer operational Capability acquisition roadmap described in Operational Analysis.
      </p>
      <p>
       Operational Analysis will also shape Validation Test campaigns, notably using operational scenarios and mission description.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/c354668558fc433fa1124e7b02e6bc7f.html">
       Perform SYSTEM NEED ANALYSIS
      </a>
     </td>
     <td>
      <p>
       The IVV strategy will order deliveries according to the&nbsp;customer value and priorities for each System&nbsp;Need capability and most important functions expected from the system.
      </p>
      <p>
       System Need Analysis will also shape verification and Validation Test campaigns, notably using System Need scenarios and System Usage as agreed with the customer.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/dd460dc8ee0b4ceba0c0135c7c103ba9.html">
       Design LOGICAL ARCHITECTURE
      </a>
     </td>
     <td>
      <p>
       Definition of the solution architecture should take into account IVVQ constraints, such as ease of progressive building and verification, observability of the behaviour, etc.
      </p>
      <p>
       Architecture-related conscerns such as performance verification, complexity and technical risk, might also impact the IVV Strategy.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/38c7424f5c11476490db367b0b43bc42.html">
       Design PHYSICAL ARCHITECTURE
      </a>
     </td>
     <td>
      <p>
       The detailled design of the solution architecture feeds IVV configurations definition. Achitectural, functional and technical dependencies may influence and constrain IVV strategy and roadmap.
      </p>
      <p>
       Functional chains and scenarios defined in the solution architecture are the basis for integration and verification test campains and test cases. Those of the functional chains and scenarios that are based on operational and system need analyses will be the reference and starting point of verification and validation tests as well.
      </p>
      <p>
       Test means definition is based on the architecture description, in terms of functional contents,&nbsp;interfaces, use scenarios, as described in the solution architecture.
      </p>
      <p>
       &nbsp;
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/21963be2f5f544798045079ed00879fa.html">
       Define &amp; enforce a PBS and Component Integration Contract
      </a>
     </td>
     <td>
      <p>
       The definition of subsystems technical contract will include definition of tests campaigns requested from subsystems, according to those architecture functional chains and scenarios that are allocated to them.
      </p>
      <p>
       Tests means specification is driven by the architecture description : interfaces to implement, components functional contents and behaviour, fu ntional chains and scenarios to enable, etc.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/d260034d335e47c98fbec6f97f023fa3.html">
       Define a Components IVVQ Strategy
      </a>
     </td>
     <td>
      <p>
       IVV Strategy is built on User and Solution Capabilities roadmap, under value analysis-originated criteria. Functional chains and scenarios describing these capabilities bridge them with functional contents and components required at each IVV step, to build the expected release configurations.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/fb4a1233e07c4fdfa6a376293041489c.html">
       Build IVV Test Suites and campaigns
      </a>
     </td>
     <td>
      <p>
       IVV Tests are built based on users operational missions and capabilities descriptions by means of operational processes and scenarios. These are transposed to System Need analysis by describing expected contribution of the system to them, resulting in need-level functional chains and scenarios.
      </p>
      <p>
       When solution architecture is defined, these functional chains and scenarios are transformed to solution-level ones, dealing with designed components functional behaviour and interfaces.
      </p>
      <p>
       Tests cases are built from these functional chains and scenarios.
      </p>
      <p>
       Note that Simulation and Specialities scenarios and models can also contribute to tests definition and solution verification.
      </p>
      <p>
       Validation preparation tasks also take benefit from need analysis and solution definition. Using an approach similar to 'Define IVV Test Suites and campaigns'.
      </p>
      <p>
       Validation use cases are mainly based on operational and system need analysis functional chains and scenarios.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/9795c75eab3749b6ba4faf74866fbe90.html">
       Build Test Means &amp; enabling Systems
      </a>
     </td>
     <td>
      <p>
       Tests means specification is driven by the architecture description : interfaces to implement, components functional contents and behaviour, fu ntional chains and scenarios to enable, etc.
      </p>
      <p>
       Note that Simulation and Specialities scenarios and models can also contribute to tests means and enabling systems definition and solution verification.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/ad6b0fea2dfc4181b89d719acdf340c4.html">
       Perform Integration
      </a>
     </td>
     <td>
      <p>
       Integration will be easier thanks to not only relying on requirements only, but also and mostly on architecture : better mastering of functional behaviour thanks to functional chains and scenarios, better default and problem analysis in identifying components flaws, etc.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/8801691110aa4b1581f8c2bfff97d5f0.html">
       Perform Verification
      </a>
     </td>
     <td>
      <p>
       Similar to Integration, verifying that user-oriented functional chains and scenarios are fulfilled.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/65458973c7084233b791dc81b9246191.html">
       Perform Solution Validation
      </a>
     </td>
     <td>
      <p>
       similar to verification.
      </p>
     </td>
    </tr>
   </table>
   <h2>
    Diagrams displaying "From Definition &amp; Design to Validation"
   </h2>
   <ul>
    <li>
     <a href="../ARCADIA/c2f4728fdb244205bf04129d1a76ec1b.html#_lOeNIJQyEeqxb5_tqwKmHg">
      4 - From Definition &amp; Design to Validation*
     </a>
    </li>
   </ul>
  </div>
 </body>
</html>
